#react params

[ghoulodont]

paw paw in transit

[everyone-with-a-para]

Haiiii! So, this isn’t a submission, but it’s a question about your server (that I probably should’ve asked before joining 😅).

I dunno if I’m just overthinking or over complicating it, but how problematic, per se, do our paras have to be to join?

Like, I sometimes consider the happenings in my paracosm problematic to some extent, and I like to joke on Nevermore (my parame) being fairly problematic, but now I’m wondering if what I consider problematic isn’t problematic… enough? If that makes sense?

I dunno, and I think I’m just confusing myself, so I wanted to make sure before actually going through with making an intro and then ending up in a space that potentially wasn’t made for me. (I really don’t want to intrude. 😰)

Anyways, I was just hoping you can shed some light on this. Thank you!

- @nevermore-grimes

There's no real rule about it, honestly it's just a safe space for all MaDD/ID in general that happens to have a focus on paras or paracosms people don't want to talk about elsewhere because of how other people might react due to para's bad actions/morally questionable storylines/"problematic" sources. But any level (or lack of) of "problematic-ness" is welcome

[jacks-manidiary]

Results of trying to talk to Nova today:

Total time was around an hour and a half maybe

All happened in thoughts although I& initially tried talking in typing

Felt like a lot of puppeteering

Came to the conclusion that it's best not to put any word for what we have going on. They have their own separate world, I& have mine&, and the type of connection we have should go unlabeled.

Talking in thoughts only sucks. We need a shared paracosm to talk through where we can visualize stuff and that can serve as a neutral territory.

Dove and Jacque would probably not react well to being contacted directly like that. Not like Nova isn't struggling with a lot of mental illnesses but Jacque especially would just have a horrible episode of some sort and Dove would get overwhelmed. So those stay as simply parames to me&.

I& do want to try out daydreaming while paying attention to the life around me&. As it is now, this reality sort of only exists as a backdrop, like a stage for daydreams and not really something properly perceived during them. Also anyone talking to me& instantly makes me& settle into Luigra's mindset, and that's not who I& really am. I& don't plan on anything like partaking in battles or talking to a para while someone else is trying to talk to me&, but I& do want to at least keep my& mental shift, you know?

[starlifeinsider]

Read More Updates from our website Starlifeinsider.com https://ift.tt/gV3dDpE Sacred Love On Starlife Saturday 31st May 2025 Written Episode Update Sacred Love On Starlife Saturday 31st May 2025 Written Episode Update The episode begins with Mahua and Chandan talking to Ranbir over the phone. Mahua happily reminds him that he had promised to visit them. Ranbir assures her that he will come and adds that even his family is excited to meet them. He tells Mahua that his mother will call her soon. When Mahua asks for his mother’s number, he replies that he’s already shared her number with his mom. Mahua asks him to speak to Adrija, but he says he’s rushing to catch a flight and will talk to her later. After the call, Mahua shares the news with Adrija, saying Ranbir is shy but promised to visit with his family. Adrija is thrilled, calling it a great moment. Chandan jokes that Adrija is now on the path to salvation. Mahua praises Ranbir, clearly impressed. Later, Meghla joins Mahua and Chandan. Mahua says that it’s fine if Ranbir’s family is wealthy—they’re not looking for money. Chandan mentions that both families should be of equal status. Mahua gets irritated and tells him not to start an argument. Chandan lightens the mood, telling her to be happy since their daughter is getting married. Mahua sarcastically reminds him it’s her daughter, not his. He smiles and agrees, saying she’s his daughter too. During breakfast, Meghla says she doesn’t enjoy singing at events. Mahua scolds her for not focusing on her studies. Adrija teases Meghla, saying she tries to imitate her but fails. Meghla replies earnestly that Adrija is her idol and she wants to be just like her. Just then, Mahua receives a call from Meher Bajwa—Ranbir’s mother. Mahua introduces herself as Adrija’s mother and warmly greets her. Meher politely responds, saying they’re doing well and that she heard Ranbir likes their daughter. She explains that they had initially arranged Ranbir’s engagement elsewhere but changed plans after learning about his feelings for Adrija. Mahua beams with joy and quickly hands the phone to Chandan. However, she gets annoyed as Chandan chats casually without getting to the point. Meher interprets this positively, saying it shows that Adrija is focused. Chandan praises Adrija and expresses how proud they are of her. Meanwhile, Harman and Param, Meher’s family members, urge her to fix the meeting. Meher suggests coming over that weekend and asks if that’s okay. Chandan says they would be honored. Meher confirms that they will fix the alliance during the visit. Chandan responds that it would be their good fortune and a matter of pride. When Meher asks if Sunday is fine, he agrees happily. Mahua can’t hold back her tears of joy. She confirms with Chandan if they’re really coming for the roka, and he nods. Adrija then gets a chance to speak to Meher directly and their conversation goes smoothly. UPCOMING Adrija gets into an argument with Chandan regarding Meghla. In the heat of the moment, Mahua reveals that Meghla was adopted. This upsets Adrija deeply, and she reacts with anger. The post Sacred Love On Starlife Saturday 31st May 2025 Written Episode Update appeared first on Starlife Insider.

[pentesttestingcorp]

API Vulnerabilities in Symfony: Common Risks & Fixes

Symfony is one of the most robust PHP frameworks used by enterprises and developers to build scalable and secure web applications. However, like any powerful framework, it’s not immune to security issues—especially when it comes to APIs. In this blog, we’ll explore common API vulnerabilities in Symfony, show real coding examples, and explain how to secure them effectively.

We'll also demonstrate how our Free Website Security Scanner helps identify these vulnerabilities before attackers do.

🚨 Common API Vulnerabilities in Symfony

Let’s dive into the key API vulnerabilities developers often overlook:

1. Improper Input Validation

Failure to sanitize input can lead to injection attacks.

❌ Vulnerable Code:

// src/Controller/ApiController.php public function getUser(Request $request) { $id = $request->query->get('id'); $user = $this->getDoctrine() ->getRepository(User::class) ->find("SELECT * FROM users WHERE id = $id"); return new JsonResponse($user); }

✅ Secure Code with Param Binding:

public function getUser(Request $request) { $id = (int)$request->query->get('id'); $user = $this->getDoctrine() ->getRepository(User::class) ->find($id); return new JsonResponse($user); }

Always validate and sanitize user input, especially IDs and query parameters.

2. Broken Authentication

APIs that don’t properly verify tokens or allow session hijacking are easy targets.

❌ Insecure Token Check:

if ($request->headers->get('Authorization') !== 'Bearer SECRET123') { throw new AccessDeniedHttpException('Unauthorized'); }

✅ Use Symfony’s Built-in Security:

# config/packages/security.yaml firewalls: api: pattern: ^/api/ stateless: true jwt: ~

Implement token validation using LexikJWTAuthenticationBundle to avoid manual and error-prone token checking.

3. Overexposed Data in JSON Responses

Sometimes API responses contain too much information, leading to data leakage.

❌ Unfiltered Response:

return $this->json($user); // Might include password hash or sensitive metadata

✅ Use Serialization Groups:

// src/Entity/User.php use Symfony\Component\Serializer\Annotation\Groups; class User { /** * @Groups("public") */ private $email; /** * @Groups("internal") */ private $password; } // In controller return $this->json($user, 200, [], ['groups' => 'public']);

Serialization groups help you filter sensitive fields based on context.

🛠️ How to Detect Symfony API Vulnerabilities for Free

📸 Screenshot of the Website Vulnerability Scanner tool homepage

Screenshot of the free tools webpage where you can access security assessment tools.

Manual code audits are helpful but time-consuming. You can use our free Website Security Checker to automatically scan for common security flaws including:

Open API endpoints

Broken authentication

Injection flaws

Insecure HTTP headers

🔎 Try it now: https://free.pentesttesting.com/

📸 Screenshot of an actual vulnerability report generated using the tool to check Website Vulnerability

An Example of a vulnerability assessment report generated with our free tool, providing insights into possible vulnerabilities.

✅ Our Web App Penetration Testing Services

For production apps and high-value APIs, we recommend deep testing beyond automated scans.

Our professional Web App Penetration Testing Services at Pentest Testing Corp. include:

Business logic testing

OWASP API Top 10 analysis

Manual exploitation & proof-of-concept

Detailed PDF reports

💼 Learn more: https://www.pentesttesting.com/web-app-penetration-testing-services/

📚 More Articles from Pentest Testing Corp.

For in-depth cybersecurity tips and tutorials, check out our main blog:

🔗 https://www.pentesttesting.com/blog/

Recent articles:

Laravel API Security Best Practices

XSS Mitigation in React Apps

Threat Modeling for SaaS Platforms

📬 Stay Updated: Subscribe to Our Newsletter

Join cybersecurity enthusiasts and professionals who subscribe to our weekly threat updates, tools, and exclusive research:

🔔 Subscribe on LinkedIn: https://www.linkedin.com/build-relation/newsletter-follow?entityUrn=7327563980778995713

💬 Final Thoughts

Symfony is powerful, but with great power comes great responsibility. Developers must understand API security vulnerabilities and patch them proactively. Use automated tools like ours for Website Security check, adopt secure coding practices, and consider penetration testing for maximum protection.

Happy Coding—and stay safe out there!

[cueburstnews]

Param Singh reacts to fans wanting Bhavika Sharma, Hitesh Bharadwaj back as the leads [Exclusive]

Ghum Hai Kisikey Pyaar Meiin is one of the top TV shows. The show recently took a leap and we saw new actors entering the show. Bhavika Sharma and Hitesh Bharadwaj played the lead role. They were loved as Rajat and Savi in the serial. Their crackling chemistry won hearts. However, the show took a leap and they quit the show. Veteran actress Rekha introduced the new story and the new actors of the…

[abdelfattah-ragab]

Angular Routing

Welcome to the book “Angular Routing”. In this book, I explain everything you need to know about Angular routing. Routing helps you to change what the user sees in a single-page app. In this book, you will learn how to implement common routing tasks. You will learn how to set up routes, retrieve route information, display 404 pages, prevent unauthorized access, and much more. By the end of this book, you will be confident working with routing in your Angular application and be able to handle all kinds of scenarios. Let us get started.

#angularrouting #guards #resolvers #canActivate #pathmatch #params #queryparams #nestedroutes #scrollpositionrestration #routerevents #routertracing

 — — — — — — — — — — — — — — — — — — — — — — — — — — -

Join our affiliate program to promote Angular and React courses.

You will only receive money when sales are made, and these should be through your link. Then you will receive 45% commission.

Sign up:

#angular #react #affiliate #commission

[thryth-gaming]

Conrad Stevenson's Paranormal PI - Review

Overall a good game and an excellent first attempt at a game. But there are some rough spots especially some poorly executed attempts at representation which I will discuss when I review each story in the spoiler section. I think I'm going to break this down into parts.

The representation issues soured much of the game for me though the atmosphere and horror were great. I'd rate it about a 2.5 or 3 out of 5. It'd be a strong 3.5 or 4 if the only issue was the gameplay slog on the Church map.

Methods

Conrad Stevenson's Paranormal PI is based around the practices of real life ghost hunting. This means the following:

Checking for unusual Electromagnetic Fields (EMF).

Checking for unusual temperatures.

Recording audio evidence

Taking photographic evidence

Recovering physical evidence

Evidence in a location will increase as you gather more evidence within a single visit.

EMF and Temperature

EMF and Temperature are straight forward to gather. When you have the necessary item in hand it will react to the environment. Sometimes you will get a little black bar that slowly fills up red. These are possible paranormal events. When the bar fills, Conrad will tell you whether or not the evidence is strange or normal.

To max out Temp or EMF evidence you need to fill up the investigation bar twice with a strange phenomenon for each type of evidence. (Temp x2 and EMF x2).

Red Herring temperature and EMF spikes tend to be stationary.

Red herrings usually occur around natural sources such as electrical outlets or devices, air conditioner vents, or doors outside.

I like to complete red herring bars so that the tool will stop responding to it.

When the EMF or Temp Spike is moving that's probably a ghost.

Poltergeists can be difficult since the temp spikes before an event and EMF after.

Once you've maxed out these evidences the investigation bar will stop appearing but the tool will still react. At this point I usually drop the tools to focus on other tools.

Audio Evidence

There's two ways to collect audio evidence. Ghosts will occasionally audibly make statements that can be recorded. This will happen randomly. You can also try to collect Electronic Voice Phenomena (EVP) by performing an EVP session with the sound recorder. This will present a list of eight questions you can prompt Conrad to ask.

Every ghost has some randomly played audio associated with it.

Intelligent ghosts and demons will respond to EVP sessions.

Shadow ghosts, residual ghosts, and poltergeists do not respond to EVP sessions.

Every ghost that responds to EVP will respond to all 8 questions.

Answers that are not in English are marked "indecipherable".

Whether or not a ghost responds to EVP is also RNG so you may need to cycle through questions for a good long while to get responses.

In order to release ghosts or exorcise a ghost you must collect a minimum number of audio samples.

Both EVP responses and unprompted sounds count toward this maximum.

Ghosts that respond to EVP have more unique sounds than you need to reach the minimum needed for releasing or exorcising a ghost.

Ghosts that don't respond to EVP must have all their sounds recorded.

Intelligent ghosts, shadow ghosts, and demons have particular audio sounds they make when they notice Conrad. These count toward the needed minimum to release a ghost.

Neither the ParaVox nor the ParaBox equipment contribute to the audio recording evidence for releasing a ghost.

If you are using the ParaVox or the ParaBox it takes more answers to get the same amount of experience.

The Paramic has a larger ranger for capturing unprompted responses but cannot be used for an EVP session.

Footsteps can be recorded for audio evidence experience but don't count toward releasing the ghost.

Poltergeist audios are usually crashes, knocking sounds, sounds like wood creaking or cracking. Poltergeist events that can be photographed also produce an audio that is needed to be recorded.

The sound recorder and paramic will continue recording even if you switch to another piece of equipment and will make a click sound when they shut off.

Photo Evidence

You will max out your photo experience on a mission for any one ghost photo and any two poltergeist event photos.

Ghosts tend to have particular routes they like to take.

If you hear footsteps that will possibly be a ghost manifesting, the type of footstep tells you what surface they're walking on.

Intelligent ghosts, shadows, and demons will react to your presence. They will look at you, run from you, or attack you.

Intelligent ghosts and demon ghosts will sometimes partially manifest. Like just the demons' eyes, or one ghosts lantern but not his body.

Residual ghosts will sometimes produce footprint sounds without being visible. You can't take photos in this case, but can give you clues as to where their route is.

Poltergeist events involve some object being thrown around. You need to photograph the object either in flight or on the ground after it lands.

Poltergeist events reset quickly so unless you were there to see it happen, you're unlikely to get the photo.

The autocam is invaluable, especially for ghosts that appear only briefly, incredibly shy, and for all poltergeists.

Keeping a photocam always in hand at an easily accessibly slot is advised.

Physical Evidence

Each of the five maps have a number of small bits of information that you can find and access through your archives on your PC between missions. Some of the possible archive notes don't appear on the map but instead appear in response to finding other pieces. These bits can be used as notes to increase the activity of specific ghosts.

They will be marked by an interact symbol when you get close. The same symbol is used for light switches and your own gear.

Each note has one or two potential spawn points where it can appear on each visit.

Once you've collected a note, it will no longer spawn at the map you found it.

Choosing Notes

While you're at the computer you can look at the accompanying emails, wiki entries, and archives to choose up to 6 notes to take into an investigation.

Notes in email or the wiki will be highlighted grey.

Some of the photos in the wiki entries for Church and Lighthouse can be clicked as notes.

Archives represent the physical evidence you find at the scene.

Chosen notes will increase the amount of activity for the associated ghost.

Each ghost has between 3 and 4 associated notes.

I believe in order to release a ghost or exorcise a demon you must start an investigation with all of that ghost's associated notes.

Only the Church and Lighthouse have wiki-entries.

I suspect the impact of notes on activity is more extreme for Demons.

Equipment

Starter Gear

Audio recorder - usable for both unprompted sounds and EVP sessions.

Photocam - has a nightvision mode, unlimited photos

EMF - needs only to be held, automatically turns on.

Thermometer - needs only to be held, automatically turns on.

Purchasble

Releasing and Exorcising Gear

These are necessary to complete the game. Most of these are smudge sticks. Admirably, none of these are described as using sage, which in the real world has been driven into endangered status due to the fad belief that it is useful for spiritual cleansings.

Mugwort Smudge Sticks (pink string) - used to release residual ghosts

Juniper Smudge Sticks (blue string) - used to release shadow ghosts

Thyme Smudge Sticks (purple string) - used to release intelligent ghosts

Rosemary Smudge Sticks (brown string) - used to release poltergeists

Palo Santo Smudge Sticks (it's a stick) - used to exorcise demons

Salt - used to exorcise demons

Good Purchases

Autocam - Will take pictures autoamtically, does not work in hand, must be set on a tripod. Has collision. You can get stuck on it. Invaluable for poltergeists, areas with lots of clutter or obstruction, shy ghosts and fast ghosts.

Paramic - Longer range than the audio recorder can't be used for EVP. Use for shadows, poltergeists, and residuals, or when you want the unprompted response.

Sometimes useful purchases

EMF Pod - This can be turned on and set in place. It will start sounding an alarm when an EMF field is near it. Don't place near generators, breaker boxes, or other sources of natural EMF. Doesn't count as EMF evidence but tells you when the ghost is near its location. You can only ever have one so it has limited usefulness.

DOTS - Projects a grid of colored dots. Normally, the dots are green. The dots turn yellow if the device is pointed at a ghost. Can be placed. Again, doesn't provide evidence on its own but can point you to where the ghost is. Can be placed or held, while held you can't use other gear because your hands are full.

Frustrating purchases

ParaVox - Can be used for EVP sessions but not audio recording. When a response is generated it produces a word from a library. This does give experience related to audio evidence, slowly, but is not audio evidence on its own. Therefore it is useless as regards trying to release ghosts or exorcise demons.

ParaBox - Same as above but with a video.

It is possible either of these pieces of gear can provide extra context or narrative. Especially for ghosts that don't speak English.

Shadows will apparently respond to these devices.

While I appreciate the added flavor and not making these required to move on, the fact that they also don't contribute to moving on is irksome and feels like a bait and switch.

Demons and Poltergeists

Demons are interesting, Judeo-Christian in model with a rather pop-culture version of the lore. One of the three demons in the game is part of the best story in the game but another of them is a cultural appropriation issue.

If a demon attacks you, Conrad will pass out. He will also lose some of the evidence he's collected and the batteries in his equipment will be dead.

Poltergeists are forgivably bland in story, they're weird things pulled from somewhere else by trauma.

Maps

Evergreen Lane (Rated 4/5)

The first map you have access to. There are four ghosts here, three human ghosts and one poltergeist. The stories give you the first taste of the in depth storytelling of this game. These are all pretty well thought through.

Elizabeth Carter is a cheerful young girl who unfortunately died young due to tuberculosis. She is a residual ghost and is not aware of her surroundings.

William Carter is Elizabeth's father and died full of anger at no one helping his children as they died from tuberculosis. He is a shadow ghost.

Robert Connor is a veteran who succumbed to PTSD and survivors guilt ending his own life. He has no particular connection to the others.

The Ghost in the Kitchen, As with all poltergeists, it is presented as some weird opportunistic thing that slipped through a crack caused by the collected trauma.

Polk Street (Rated 3.5/5)

Polk Street's stories are also pretty in depth, but they are a bit soured by the fact that it feels like Deborah's abuse is treated as a symptom of her mental illness. It is a difficult line to manage and I'm not sure it truly crosses the line, but it came close enough for me to be a bit uncomfortable. This may be personal bias, however, as abusive parents are a bit of a hated thing for me, blame being a teacher.

David Allen was abused by his stepmother and then died at age 31 while hanging out with friends. He appears a young boy ghost and is an intelligent ghost who regard Conrad with curiosity and friendliness.

Deborah Allen is David's stepmother who was dealing with substance abuse and mental illness. It is at least implied that she ended her own life in her 30s.

Harold Wagner is an old man who died many years after the death of his wife after they had lived together 40 years. He is a residual bound her by loneliness and deep grief.

The Ghost in the Garage, another poltergeist, not much story, drawn here by the death and trauma on the site.

Spruce Street Church (2/5)

The gameplay really suffers on this map. Many of the ghost suffer poorly balanced activity. You can spend a lot of time waiting for the ghost to appear or give audio. This feels like a mix of the large areas and the RNG nature of how activity is produced. It is a major point of lag in the game.

On top of that are the uses of a Native American ghost but without any of the narrative depth that we find in the other stories. He's sort of just there and feels sort of like a footnote of the demon's story and I feel like they could have used a more general name for the demon rather than use a name that the culture has asked people not to use in fiction. This was especially disappointing after the way they avoided using sage as a smudge stick and how they handled the other stories.

The Segerstein, Ulrich, the Williams, and LeFebre stories are all very well done and evocative. I do wish a less appropriation-tainted version of the demon could be better linked to more of the troubles in the area similar to the situation in Jefferson Street.

Pastor Jacob Johnson is a minister who was watching his congregation shrink over time and became fearful for the spiritual safety of the people around him. He is a residual ghost.

John Ulrich is a gravedigger and graverobber. Unfortunately his son was killed when the son investigated what he was doing and two angry mourners shot and killed the boy by accident. He is a shadow ghost.

Ezra Segerstein was a groundskeeper from an unknown time who started haunting the land after the Segerstein family was evicted in the 1950s despite having maintained the grounds for generations at that point. He is an intelligent ghost.

Alice Williams was a woman in an abusive marriage in the 1940s. She had a lover outside the marriage and had a son with her lover. In an argument with her abuser she admitted her son was not his and the abuser killed them both. She is a residual ghost.

Timothy Williams is Alice's son who was killed by her husband. Though investigating him it feels like the implication is he was playing superhero and fell killing himself in an accident. He is a residual ghost.

Pierre Lefebre is an architect who designed a mausoleum that he expected would be open to the public, however the mausoleum was then used only for the elites and he received some of the blame. After dying in a carriage accident he was buried in the mausoleum and now haunts lighting candles in a silent protest to the way his work was tainted. He's an intelligent ghost.

Red Eyes is an indigenous ghost of unknown name who was already around when the first colonists arrived. We're never given a name and we're told he's been resisting/guarding against the demon for centuries. He is a shadow ghost.

The demon in the woods uses a name that is considered inappropriate to use for pop culture and is said to have been a cannibal spirit that was summoned here by some cult.

Jefferson Street (5/5)

This is the best crafted story of the entire set. All the ghosts are tied together and there's a very neat point of Rhonda's ghost avoiding the parts of the house her mother's ghost haunts most of the time, though she will go into the girl's room and turn the crosses upside down as part of her effort to try to warn people about the demon and do what she can to protect the current residents.

Rhonda DaFoe was a young woman who got interested in the occult and ended up accidentally summoning a real demon which then possessed her. Her behavior immediately changed and she eventually killed her entire family before killing herself in jail while waiting for trial. She is a shadow ghost.

Kathy DaFoe was Rhonda's mother and kept trying to explain away Rhonda's change in behavior. She is a residual ghost.

The demon in the basement is the architect of the entire tragedy and is working to possess the child of the current residents.

Barr Harbor Lighthouse (2.5/5)

The gameplay issues of Spruce Street occur a little bit here in places, but not nearly as bad as a lot of the locations are a bit more contained. Two of the major locations are fairly easily missed, namely the slave cabins and the sea cave. Gameplay actually went a lot smoother than Spruce Street for most ghosts.

The representation issue happens here again. I will note that Douglas Murdock is the only human ghost that Conrad has no patience for, but it feels like they wanted to try to do some Black representation and jumped to slavery as the subject. However, George comes feels like a footnote to Douglas's story. It is admittedly an attempt to point out that slavery existed in northern states as well and that people weren't willing to do too much despite their discomfort with it. It's hard for me to express how much this soured the map for me. Having one of the release multiple choice questions being a Beatles joke especially was aggravating.

I'm not sure the Slavic cultures have a problem with using Rulsalka in pop culture, but I'd still encourage using less culturally specific terms for the demon just for consistency with Jefferson Street and to avoid using that name in Spruce Street.

Deidre Hurley is the wife of one of the lighthouse keepers. She died in childbirth along with her last child. She is trying to see her baby and seems to still be in pain from the trauma of her death. She is an intelligent ghost and probably was aware of when her son Eli died as well.

Eli Hurley is one of the children of Deidre Hurley, he was roughhousing with his brother in the lighthouse and fell over a railing dying in the fall. He is still playing in the lighthouse. He is a shadow ghost.

Douglas Murdock was one of the first two lighthouse keepers and a disgraced politician who very likely killed his wife. Despite the locals being against slavery he made an effort to go south and buy slaves, one of whom he beat to death for a petty reason. As a result the other lighthouse keeper murdered him as a matter of vigilante justice. He is a residual ghost.

George is the slave whom Douglas Murdock murdered. He was a porter. We don't know much else about him. He is a residual ghost.

Rene Novak was from a later family and was the one to start holding ghost tours around the light house grounds. She has continued to haunt the area out of a sense of nostalgia and love for her home. She is a residual ghost.

Dr Arthur Gideon is a civil war doctor who was set up in the general hospital nearby which is now being used as a barn. This makes some question that this is somewhere close enough to the fighting that battlefield injuries were coming here and is part of why I feel like this isn't exactly Earth. He is an intelligent ghost.

Mary Walsh was a coast guard operator during a war, probably World War II or its equivalent. Her newlywed husband went into the military (I'm not certain which branch) and died overseas. She was well regarded for her diligence but spent the rest of her life heartbroken living only for her work. She is a shadow ghost.

Melanie Peters was a cheerleader who was murdered by a demon possessed serial killer. We don't know too much about her personally, but we hear a bit about the night she died. She was likely sacrificed to the demon. She is a residual ghost.

The demon in the sea cave is tied to Melanie's death and it is implied she has been causing the death of teenaged couples at least once a year for decades.

[brainyrainy]

If we panic when in trouble, life can be like a drowning person struggling to survive but it will usually be in vain. Frantic struggling drains our strength eventually taking us down under.

After all efforts had failed, I and my ego, surrendered to something infinitely greater than myself. Most people call  that power 'God', 'Waheguru', 'Param-Atma' etc. Just like an exhausted child snuggles into the arms and embrace  of a loving parent, I felt carefree and unconcerned about current and future situations.

Then something miraculous happened, my mind began to be unburdened and my energy levels began to rise. I was able to think more clearly. Instead of reacting, I began to respond, and that too positively.

While retaining my convictions and sanity, I just abandoned the struggle. Did it mean,  the problems went away? No, I just learned to cope. 

Gradually sinking, when I hit rock bottom I realised that the only way is up.  Left for dead or finished, I discovered I had begun to float.

Today, materially I am just a fraction of my former self, but emotionally and spiritually I have blossomed. The reason is not difficult to see, I awoke to the Guru's message 'All has to be first lost, before we are found'.

[this-week-in-rust]

This Week in Rust 476

Hello and welcome to another issue of This Week in Rust! Rust is a programming language empowering everyone to build reliable and efficient software. This is a weekly summary of its progress and community. Want something mentioned? Tag us at @ThisWeekInRust on Twitter or @ThisWeekinRust on mastodon.social, or send us a pull request. Want to get involved? We love contributions.

This Week in Rust is openly developed on GitHub. If you find any errors in this week's issue, please submit a PR.

Updates from Rust Community

Foundation

A Q4 Recap & 2022 Reflection from Rebecca Rumbul

Project/Tooling Updates

rust-analyzer changelog #162

fltk-rs in 2022

shuttle - Release v0.8.0

This Week in Fyrox

gitoxide - The year in retrospective, and what's to come

The AeroRust community - 3 years birthday (and the roadmap for 2023)

SeaQuery 0.28.0 - A dynamic query builder for SeaORM

Databend 2022 Recap

Observations/Thoughts

State Machines III: Type States

Rust — vim — code completion

How to Test

Embedded Rust and Embassy: DMA Controllers

Parsing TFTP in Rust

Rustdoc JSON in 2022

From PHP to Rust: Migrating a REST API between these two languages. (Part I)

React + Rust + Wasm: Play an Animated 3D Model

Open Source Grindset Explained (with a Rust example)

Rust Walkthroughs

Building a Simple DB in Rust - Part 1

Microservices with Rust and WASM using Fermyon

Compiling Brainfuck code - Part 4: A Static Compiler

Rusty Circuit Breaker 🦀

Zero-dependency random number generation in Rust

Miscellaneous

Rust 101: an open-source university course

[video] If Rust Compiles, It WORKS (Testing not needed 📚)

[video] Introduction to Axum

[video] Ergonomic APIs for hard problems - Raph Levien

Crate of the Week

This week's crate is Sniffnet, a cross-platform GUI application to analyze your network traffic.

Thanks to Gyuly Vgc for the suggestion!

Please submit your suggestions and votes for next week!

Call for Participation

Always wanted to contribute to open-source projects but did not know where to start? Every week we highlight some tasks from the Rust community for you to pick and get started!

No calls for participation this week. Keep an eye out for more places to contribute next week!

If you are a Rust project owner and are looking for contributors, please submit tasks here.

Updates from the Rust Project

291 pull requests were merged in the last week

CFI: monomorphize transparent ADTs before typeid

account for match expr in single line

account for macros in const generics

account for multiple multiline spans with empty padding

adjust message on non-unwinding panic

allow trait method paths to satisfy const Fn bounds

always suggest as MachineApplicable in recover_intersection_pat

detect diff markers in the parser

detect when method call on LHS might be shadowed

dont use --merge-base during bootstrap formatting subcommand

emit fewer errors on invalid #[repr(transparent)] on enum

encode spans relative to the enclosing item -- enable on nightly

error parsing lifetime following by Sized and message + between them

fix confusing diagnostic when attempting to implementing trait for tuple

format only modified files

on unsized locals with explicit types suggest &

only deduplicate stack traces for good path bugs

give the correct track-caller location with MIR inlining

implement allow-by-default multiple_supertrait_upcastable lint

improve heuristics whether format_args string is a source literal

make trait/impl where clause mismatch on region error a bit more actionable

merge multiple mutable borrows of immutable binding errors

partially fix explicit_outlives_requirements lint in macros

properly calculate best failure in macro matching

provide a better error and a suggestion for Fn traits with lifetime params

provide local extern function arg names

recover fn keyword as Fn trait in bounds

remove unreasonable help message for auto trait

silence knock-down errors on [type error] bindings

suggest Pin::as_mut when encountering borrow error

suggest impl Iterator when possible for _ return type

suggest rewriting a malformed hex literal if we expect a float

suppress errors due to TypeError not coercing with inference variables

trim more paths in obligation types

miri: cargo-miri: use rustc to determine the output filename

miri: handle unknown targets more gracefully

miri: simplify path joining code a bit

miri: support using a JSON target file

miri: tweaks to retag diagnostic handling

use some more const_eval_select in pointer methods for compile times

more inference-friendly API for lazy

more verbose Debug implementation of std::process:Command

add #[inline] markers to once_cell methods

unify id-based thread parking implementations

available_parallelism:gracefully handle zero value cfs_period_us

catch panics/unwinding in destruction of thread-locals

cargo: asymmetric tokens

cargo: reasons for rebuilding

clippy: fix false negative in needless_return

clippy: fix match_single_binding suggestion introducing an extra semicolon

clippy: move mutex_atomic to restriction

rust-analyzer: derive Hash

rust-analyzer: enum variant discriminants hints

rust-analyzer: diagnose private assoc item accesses

rust-analyzer: diagnose private field accesses

rust-analyzer: implement yeeting

rust-analyzer: fall back to inaccessible associated functions and constants if no visible resolutions are found

rust-analyzer: improve exit point highlighting for for and while loops in tail position

rust-analyzer: merge multiple intersecting ranges

rust-analyzer: prefix prelude items whose name collides in current scope

rust-analyzer: type check unstable try{} blocks

rust-analyzer: support multi-character punct tokens in MBE

rust-analyzer: write down adjustments introduced by binary operators

Rust Compiler Performance Triage

Fairly busy week with some massive performance improvements at the expense of some significant albeit smaller regressions. The main wins came in a long-standing PR from @cjgillot to enable encoding spans in metadata relative to their enclosing item. This causes more work in full compilation which causes some regressions up to 5% but can lead to very large wins in incremental compilation scenarios (up to ~70%). For example, the clap crate compiles 68% faster after a small 1 line change than it did previously.

Triage done by @rylev. Revision range: b38a6d..b43596

Summary:

(instructions:u) mean range count Regressions ❌ (primary) 1.6% [0.3%, 4.6%] 97 Regressions ❌ (secondary) 1.8% [0.2%, 7.6%] 60 Improvements ✅ (primary) -9.7% [-68.7%, -0.2%] 53 Improvements ✅ (secondary) -1.7% [-15.3%, -0.1%] 62 All ❌✅ (primary) -2.4% [-68.7%, 4.6%] 150

1 Regressions, 1 Improvements, 4 Mixed; 1 of them in rollups 47 artifact comparisons made in total

Full report here

Approved RFCs

Changes to Rust follow the Rust RFC (request for comments) process. These are the RFCs that were approved for implementation this week:

No RFCs were approved this week.

Final Comment Period

Every week, the team announces the 'final comment period' for RFCs and key PRs which are reaching a decision. Express your opinions now.

RFCs

No RFCs entered Final Comment Period this week.

Tracking Issues & PRs

[disposition: merge] Only include stable lints in rustdoc::all group

[disposition: merge] Don't derive Debug for OnceWith & RepeatWith

[disposition: merge] PhantomData layout guarantees

[disposition: merge] Add O(1) Vec -> VecDeque conversion guarantee

[disposition: merge] Stabilize ::{core,std}::pin::pin!

[disposition: merge] Stabilize main_separator_str

[disposition: merge] Loosen the bound on the Debug implementation of Weak.

New and Updated RFCs

No New or Updated RFCs were created this week.

Call for Testing

An important step for RFC implementation is for people to experiment with the implementation and give feedback, especially before stabilization. The following RFCs would benefit from user testing before moving forward:

No RFCs issued a call for testing this week.

If you are a feature implementer and would like your RFC to appear on the above list, add the new call-for-testing label to your RFC along with a comment providing testing instructions and/or guidance on which aspect(s) of the feature need testing.

Upcoming Events

Rusty Events between 2023-01-04 - 2023-02-01 🦀

Virtual

2023-01-04 | Virtual (Indianapolis, IN, US) | Indy Rust

Indy.rs - with Social Distancing

2023-01-04 | Virtual (Stuttgart, DE) | Rust Community Stuttgart

Rust-Meetup

2023-01-05 | Virtual (Charlottesville, VA, US) | Charlottesville Rust Meetup

Part 2: Exploring USB with Rust

2023-01-10 | Virtual (Dallas, TX, US) | Dallas Rust

Second Tuesday

2023-01-11 | Virtual (Boulder, CO, US) | Boulder Elixir and Rust

Monthly Meetup

2023-01-12 | Virtual (San Francisco, CA, US; Stockholm, SE; New York, NY US) | Microsoft Reactor San Francisco | Microsoft Reactor New York

Crack code interview problems in Rust - Ep. 1 | Stockholm Mirror | New York Mirror

2023-01-12 | Virtual (Nürnberg, DE) | Rust Nuremberg

Rust Nürnberg online

2023-01-14 | Virtual | Rust GameDev

Rust GameDev Monthly Meetup

2023-01-16 | Virtual (San Francisco, CA, US; São Paulo, BR; New York, NY, US) | Microsoft Reactor San Francisco and Microsoft Reactor São Paulo and Microsoft Reactor New York

Primeros pasos con Rust - Qué es y Configuración el entorno de desarrollo | São Paulo Mirror | New York Mirror

2023-01-17 | Virtual (Berlin, DE) | OpenTechSchool Berlin

Rust Hack and Learn

2023-01-17 | Virtual (San Francisco, CA, US; São Paulo, BR, New York, NY, US) | Microsoft Reactor San Francisco and Microsoft Reactor São Paulo and Microsoft Reactor New York

Primeros pasos con Rust - Creación del primer programa de Rust | *São Paulo Mirror | New York Mirror

2023-01-17 | Virtual (Washington, DC, US) | Rust DC

Mid-month Rustful

2023-01-18 | Virtual (San Francisco, CA, US; São Paulo, BR; New York, NY US) | Microsoft Reactor San Francisco and Microsoft Reactor São Paulo and Microsoft Reactor New York

Primeros pasos con Rust: QA y horas de comunidad | Sao Paulo Mirror | New York Mirror

2023-01-18 | Virtual (Vancouver, BC, CA) | Vancouver Rust

Rust Study/Hack/Hang-out

2023-01-26 | Virtual (Charlottesville, VA, US) | Charlottesville Rust Meetup

Rust Lightning Talks!

2023-01-31 | Virtual (Dallas, TX, US) | Dallas Rust

Last Tuesday

2023-02-01 | Virtual (Indianapolis, IN, US) | Indy Rust

Indy.rs - with Social Distancing

Asia

2023-01-15 | Tokyo, JP | Tokyo Rust Meetup

Property-Based Testing in Rust

Europe

2023-01-12 | Enschede, NL | Dutch Rust Meetup

Rust Meetup - Subject TBA

2023-01-20 | Stuttgart, DE | Rust Community Stuttgart

OnSite Meeting

2023-01-25 | Paris, FR | Rust Paris

Rust Paris meetup #55

North America

2023-01-05 | Lehi, UT, US | Utah Rust

Lightning Talks 'n' Chill (a.k.a. Show & Tell), with Pizza!

2023-01-09 | Minneapolis, MN, US | Minneapolis Rust Meetup

Happy Hour and Beginner Embedded Rust Hacking Session (#2!)

2023-01-11 | Austin, TX, US | Rust ATX

Rust Lunch

2023-01-17 | San Francisco, CA, US | San Francisco Rust Study Group

Rust Hacking in Person

2023-01-26 | Copenhagen, DK | Copenhagen Rust group

Rust Hack Night #32

2023-01-26 | Lehi, UT, US | Utah Rust

Building a Rust Playground with WASM and Lane and Food!

If you are running a Rust event please add it to the calendar to get it mentioned here. Please remember to add a link to the event too. Email the Rust Community Team for access.

Jobs

Please see the latest Who's Hiring thread on r/rust

Quote of the Week

You haven’t “fooled” rustc, you are using unsafe code. Unsafe code means that all you can do is fool yourself.

– Frank Steffahn on rust-users

Thanks to Quine Dot for the suggestion!

Please submit quotes and vote for next week!

This Week in Rust is edited by: nellshamrell, llogiq, cdmistman, ericseppanen, extrawurst, andrewpollack, U007D, kolharsam, joelmarcey, mariannegoldin, bennyvasquez.

Email list hosting is sponsored by The Rust Foundation

Discuss on r/rust

[yazilimdefteri]

React url’den dinamik değişken göndermek, params

Uyeleri listelediğimde (1 durum)( tıkladıgım üyenin id’sini baska bir komponente (2 numara ile gösterilen )url ile gönderip olarada yakalamak istiyorum amac bu. Tıkladıgım id urlde gözükecek şunun gibi http://localhost:3001/edit/1

1. App js (updateuser diye bir component yaptık detay sayfası olarak dusunebilirz)componenti import ediyoruz

import UpdateUser from './components/updateUser'

ve router içinde url yapısını şu şekilde ayarlyoruz. (/edit/1 dersek UpdateUser componenti çıkacak)

<Route exact path='/edit/:id' component={UpdateUser} />

2. Users compomentinden de id göndereceğiz. Linki import etmeniz lazım onları artık söylemiyorum normal routerin özelliği anlattık

Sonra şu alttaki butonu ekliyoruz. id değişkenini edit/değişkenneyseo seklinde gönderiyor.

<Link to={`edit/${id}`} className="btn btn-dark"> Detay </Link>

3. Updateuser diye bir komponent olustuyoruz. Burası da id urlden yakaladığımız sayfa

import React, {Component} from 'react'; class UpdateUser extends Component {    render() {        console.log(this.props.match.params.id)        return (            <div>                <h3>Update</h3>                <p>Gelen değer {this.props.match.params.id}</p>            </div>        );    } } export default UpdateUser;

[codewithnazam]

React Router Tutorial for Beginners

#React #reactjs

React Router is a popular routing library for the React.js library. It allows developers to easily create Single Page Applications (SPAs) with multiple views, by providing a way to handle routing and rendering of components based on the URL. In this article, we’ll cover the basics of React Router and how to use it to build a basic SPA. What is Routing? Why use React Router? Installing React…

[transcendent-paras]

For some reason I vividly remember in the 4th grade daydreaming, but only half daydreaming and thinking "I'm able to daydream and still do all these tasks (I was packing up and getting ready to leave)" and getting so excited realizing I could 'fake' being in the moment while being so consumed by my daydream. Its astonishing to me that I never saw any red flags over that moment even years later until recently discovering MaDD a few years ago. It’s so... jarring how easily my daydreaming went from a fun pass time to so consuming, and how young I was too

[techomoro]

Scroll Page to the Top When Change in States or Props or URL Params - React

Scroll Page to the Top When Change in States or Props or URL Params – React

Assume that you are working on a product details page for an E-commerce website made using React. You scroll down to the related products section and click another product. The product and the URL change but the page do not scroll to the top. So here, we are discussing a way to scroll the page to the top when there is a change in states or props or URL params. The problem is visualized with a…

[lazyduchess]

[TS2] Need Solve Hotkeys

Overview

This mod mimics the behavior of the need solving keyboard shortcuts present in the Stories games and the later Sims games, to a certain extent.

The Needs panel will now display the associated keyboard shortcut to automatically solve each need.

Should also work with Servos, PlantSims and toddlers, however toddlers are naturally a little limited in what they can do to take care of themselves.

It's compatible with TwoJeffs' SmartBeds, if you'd like the energy shortcut to be smarter about which bed it chooses.

Download

SimFileShare | Patreon

Pre-Requisites and Installation

The mod will not work without the latest version of either Sims2RPC or RPCLib, so get either of them before installing this mod. This also means you must have the Windows version of Mansion & Garden/UC/Fun with Pets.

Installation instructions are included in a Readme.txt file inside of the attached zip.

Translations

English

Dutch (By Fire_Flower at @fireflowersims)

Spanish (By @borjabpv)

Russian (By @renfree)

Polish (By @jellymeduza)

French (By pL#8850 on Discord)

German (By Hendrik McSims#5060 on Discord)

Brazilian Portuguese (By @boringbones)

For Modders

This section assumes you know how to create a global mod and are familiar with modding.

If you'd like to make a mod that reacts to key presses, you will need to create a custom text file in "TSBin/mods" named "x_hotkeys.cfg", with x being whatever you want. For example, "ld_coolmod_hotkeys.cfg".

The included "ld_needsolve_hotkeys.cfg" file contains comments on the syntax of the file and how to write your own or rebind existing ones.

You also need the "ld_HotkeyController.package" file included in this mod for it to work. Feel free to redistribute it with your own mods.

Next, you need to create a new global object and set its category to -14457 in its Init function. Then, create a "CT - Hotkey" private BHAV.

This BHAV will get called everytime there is a key press, with the SimAntics value associated to they keypress passed as the Param 0.

[the-indigo-cosm]

MADD + Plurality?

Hello,

I have struggled with MADD all my life and have very vivid memories of using daydreaming to cope with isolation and verbal abuse since the age of 5. However I've noticed over the past few months as my depression worsened, my parames/paraselves have gotten much more vivid, complex, and harder to 'shake off' when I need to get back to focusing on the real world. I'm sure that dissociation plays into the mix. I've also been feeling like instead of me controlling the parames through creating storylines and planning reactions from them, they just...do stuff on their own I guess? They react to stuff both within the paracosm and in the real world without any forethought from me. Usually it's independent thoughts or emotions that they're having, so my IRL day isn't disrupted, but on two occasions I've felt as if they were controlling my body's reactions to things and that I was not the one moving my muscles. I just...idk. I'm definitely not looking for a diagnosis and don't want to appropriate terms from the DID and OSDD communities. But lately I've felt like I fall somewhere sloppily in the middle of MADD and a dissociative disorder, and I'm scared. And if anyone could offer support, clarity, or their 2 cents on it all, I would really appreciate it.